Method for providing read data flow control or error reporting using a read data strobe

ABSTRACT

Disclosed herein are system, apparatus, methods and/or combinations and sub-combinations thereof, for using a read data strobe signal received at a host device from a peripheral device to convey variable latency (flow) control or report an error in the data content read from the peripheral device. Reception of the read data strobe signal before a predetermined maximum latency time, provides variable latency control back to the host by indicating when valid data is available for capture. If the read data strobe signal is not received before expiration of a predetermined maximum latency time, the peripheral controller is indicating a read data error back to the host.

FIELD OF THE INVENTION

This invention relates to systems having peripheral devices coupled tohost devices through an interface. In particular, the invention relatesto providing variable latency (or flow) control and reporting errors forread data from a peripheral device, using a read data strobe signalreceived at a host device.

BACKGROUND

Modern electronic systems include volatile or non-volatile memory thatis used to store code or application data processed by applicationsoftware. Recent developments of flash non-volatile memory (Flash) anddynamic random access memory (DRAM) have reduced data corruption, suchthat data reliability is very high and in most cases data is read out ofthese devices assuming no corruption. Even with these memory types, astatus register in the memory may carry information about any data readfailures that do occur. However, a host usually does not read the statusafter every data access due to additional communication time overhead inthe system that would reduce system performance.

Corruption in the data read at the peripheral may result in erroneouscode or data transmission to a processing device, e.g., a centralprocessing unit (CPU) or the like. Processing erroneous code or data inturn can lead to system failures, which are hard to detect. And,recovery from system failure is very time consuming. For example, if amemory is used in a network, this system failure could cause significantdown time, which is not acceptable in many systems. Such systems needimmediate notification of any detected read error and provide a signalseparate from the memory read data to indicate to the host that a readerror has occurred.

Many systems also transfer data at high speeds, such that the period oftime during which each bit of data is valid is very short, making itdifficult for the host to know the optimal point in time to capturevalid data. These systems often include a signal separate from the datato indicate the optimal point in time to capture valid data. This signalis often referred to as a receive data clock (RDC), a data-in-out strobe(DQS), or read data strobe (RDS). While the RDS provides an indicationof the best point within a clock cycle to capture data, the RDS isexpected to transition between signal levels within a fixed number ofclocks following the beginning of a read access and to continue regulartransitions during any set of sequential read accesses.

SUMMARY

Provided herein are system, apparatus, methods and/or combinations andsub-combinations thereof, for using a single read data strobe (RDS)signal received at a host device from a peripheral device to performmultiple functions that indicate a variable latency from the start of aread access to when data is first valid, to provide a timing referencerelative to the read data for the optimal point in time to capture thedata, to control the flow of transfers in a series of read accesses byindicating when subsequent data is again valid, and to report any errorin the read access of the peripheral device.

An embodiment includes a method for interpreting information from theRDS signal at the host interface. The method is based on counting clockpulses until a RDS signal transition between voltage levels is receivedat the peripheral controller of the host interface. According to oneoperative mode, data is transmitted without error when the RDS signaltransitions are received at expected time intervals. According to asecond operative mode of this embodiment, an error is communicated tothe host and data is not transmitted from the peripheral, when the RDSsignal is not received before expiration of a maximum waiting time atthe peripheral controller. According to a third operative mode of thisembodiment, the data is sent only when the RDS signal transitions, andthese transitions may vary in the time interval between the beginning ofa read access and first transfer of data or between subsequent datatransfers in a series of transfers, to control the flow (rate) oftransfers.

A further embodiment includes a method for detecting the read data errorusing a peripheral device and a received RDS signal. The operationincludes loading a counter with a predetermined maximum waiting time andcounting down until the RDS signal transition is received from theperipheral device. If the counter has counted down to zero beforereception of the RDS signal transition at the peripheral controller, anerror response is sent to the processing unit of the host device with nodata transmission. Otherwise, valid data is captured and transmitted tothe host.

Further features and advantages of the invention, as well as thestructure and operation of various embodiments of the invention, aredescribed in detail below with reference to the accompanying drawings.It is noted that the invention is not limited to the specificembodiments described herein. Such embodiments are presented herein forillustrative purposes only. Additional embodiments will be apparent topersons skilled in the relevant art(s) based on the teachings containedherein.

BRIEF DESCRIPTION OF THE DRAWINGS/FIGURES

The accompanying drawings, which are incorporated herein and form partof the invention description, illustrate the present invention and,together with the detailed description, further serve to explain theprinciples of the invention and to enable a person skilled in therelevant art(s) to make and use the invention.

FIG. 1 illustrates an electronic device subsystem including a hostcoupled to a peripheral device.

FIG. 2 illustrates interface connections between a host interface and aperipheral interface.

FIG. 3 illustrates a peripheral interface, according to an embodiment ofthe disclosure.

FIG. 4 illustrates a host interface, according to an embodiment of thedisclosure.

FIG. 5 is a flow diagram depicting a method, according to an embodimentof the disclosure.

FIGS. 6, 7, and 8 are timing diagrams, according to an embodiment of thedisclosure.

The features and advantages of the present invention will become moreapparent from the detailed description set forth below when taken inconjunction with the drawings, in which like reference charactersidentify corresponding elements throughout. In the drawings, likereference numbers generally indicate identical, functionally similar,and/or structurally similar elements. The drawing in which an elementfirst appears is indicated by the leftmost digit(s) in the correspondingreference number.

DETAILED DESCRIPTION

This description discloses one or more embodiments that incorporate thefeatires of this invention. The disclosed embodiment(s) merely exemplifythe invention. The scope of the invention is not limited to thedisclosed embodiment(s). The invention is defined by the claims appendedhereto.

The embodiment(s) described, and references in the description to “oneembodiment”, “an embodiment”, “an example embodiment”, etc., indicatethat the embodiment(s) described may include a particular feature,structure, or characteristic, but every embodiment may not necessarilyinclude the particular feature, structure, or characteristic. Moreover,such phrases are not necessarily referring to the same embodiment.Further, when a particular feature, structure, or characteristic isdescribed in connection with an embodiment, it is understood that it iswithin the knowledge of one skilled in the art to use such a feature,structure, or characteristic in connection with other embodimentswhether or not explicitly described.

Embodiments of the invention may be implemented in hardware, firmware,software, or any combination thereof. Embodiments of the invention mayalso be implemented as instructions stored on a machine-readable medium,which may be read and executed by one or more processors. Amachine-readable medium may include any mechanism for storing ortransmitting information in a form readable by a machine (e.g., acomputing device). For example, a machine-readable medium may includeread only memory (ROM); random access memory (RAM); magnetic diskstorage media; optical storage media; flash memory devices; electrical,optical, acoustical or other forms of propagated signals, and others.Further, firmware, software, routines, instructions may be describedherein as performing certain actions. However, it should be appreciatedthat such descriptions are merely for convenience and that such actionsin fact result from computing devices, processors, controllers, or otherdevices executing the firmware, software, routines, instructions, etc.

Before describing such embodiments in more detail, however, it isinstructive to present an example environment in which embodiments ofthe present invention may be implemented.

FIG. 1 illustrates a system 100, according to an embodiment. In oneexample, system 100 is an electronic device subsystem including a hostdevice 102 coupled to a peripheral device 104.

Host device 102 may be a host system-on-a-chip (SoC). Host device 102may include a host interface 106 coupled to a central processing unit(CPU) 108 through an internal system bus 112. CPU 108 can be part of,but not limited to, a personal laptop or desktop computer or a mobiledevice (not shown).

Peripheral device 104 may include a peripheral device interface 110.

In one example, host device 102 may communicate with peripheral device104 through an interface bus 114, which connects host interface 106 toperipheral interface 110.

In one example, peripheral device 104 can be, but is not limited to, aNAND Flash memory, a NOR Flash memory, or a DRAM memory.

It is to be appreciated that, while FIG. 1 shows only one host interface106, host device 102 may include additional host interfaces.

FIG. 2 illustrates detailed interface connections between host interface106 and peripheral interface 110, according to an embodiment.

In this example, interface bus 114 connects host interface 106 toperipheral interface 110 through one or more channels or signal pathsbetween peripheral device 104 and host device 102. It should be notedthat the term “signal” may be used interchangeably herein to refer tothe actual information or the channel connection itself that is used totransmit the signal information, as it may be apparent to one skilled inthe relevant art.

In the example shown, there may be four uni-directional channels(220-226) from host interface 106 to peripheral interface 110 and oneuni-directional channel 230 from peripheral interface 110 to hostinterface 106. A chip select channel 220 may be used to select one ofmany chips in peripheral device 104 during an operation. A clock signalchannel 222 may be used as a reference clock from host device 102 toperipheral device 104. A control channel 224 transmits controlinformation. An address channel 226 may be used to transmit the addresslocation to peripheral interface 110. A read data strobe (RDS) signalmay be transmitted through channel 230 from peripheral interface 110 tohost interface 106. In one example, the RDS signal is used to validatedata transmission and indicate read error or variable timing informationto host device 102.

In one example, there may be a bi-directional channel (228) fromperipheral interface 110 to host interface 106. Data in/out signals maybe transmitted through bi-directional channel 228 to send data fromperipheral interface 110 to host interface 106. While in this examplethe data in/out signal is transmitted through bi-directional channel228, it is to be appreciated that two different uni-directional channelsmay also be used in place of the bi-directional channel. The control,address, data in/out channels may also share a common set of signals viatime division multiplexing.

FIG. 3 is a more detailed internal block diagram of peripheral interface110, according to an embodiment. In this example, peripheral interface110 may include several logic blocks coupled to one another throughinterface connections 340. For example, input logic 342, control logic344, function block 346, and output logic 348.

In one example, input logic block 342 receives chip select signal fromchannel 220, the reference clock signal from channel 222, controlinformation from channel 224, address information from channel 226, andhave data input or output signals connect through channel 228.

In one example, function block 346 determines a function performed byperipheral device 104.

In one example, output logic 348 is responsible for communicating datain channel 228 and RDS signal in channel 230 back to host device 102.

In one example, control logic block 344 communicates with input logic342, that may determine the time and order of different functionexecution at peripheral interface 110.

Output logic block 348 may include a data output buffer 350, latencycontrol mechanism 352, and error detection block 354. Data output buffermay store data for transmission to host device 102 (FIG. 1) through datain/out channel 228. Latency control mechanism 352 may manage the RDSoutput so that it matches the time when data is ready for transmission,and communicates the RDS signal back to host device 102. Error detectionblock 354 may be used to identify when there is an error in the data andcommunicates with latency control mechanism 352 through channel 356 toprevent transmission of the RDS signal.

FIG. 4 is a more detail internal block diagram of host interface 106,according to an embodiment. In this example, host interface 106 mayinclude several logic blocks coupled to one another through interfaceconnections 460. The logic blocks may include input logic 462, controllogic 464, and output logic 466.

In one example, output logic 466 can be used to transmit one or moresignals, e.g., chip select, reference clock, control, address, and dataout, from host interface 106 to peripheral interface 110 (FIG. 1),through channels 220 to 228.

In one example, input logic 462 receives and processes data throughchannel 228 and the RDS signal through channel 230 from the peripheral104, a host internal bus interface 468 configured to communicate withthe central processing unit 108 through internal system bus 112 byreceiving the internal system clock through channel 470, address datathrough channel 472, and transmitting read data through channel 474 anda response signal through channel 476 to indicate valid or erroneoustransmission. In one example, a control logic 464 may determine the timeand order of different function execution at host interface 106.

Input logic 468 may further comprise a data input buffer 480 responsiblefor receiving the read data through channel 228 from peripheral device104, an RDS detect and clock generation circuit 482, which, in oneexample, may receive the RDS signal through channel 230 and delay it sothat its rising edge is shifted to occur in the middle of the valid datapacket; and a latency error detection circuit 484, which can detectwhether an error has occurred. The delayed RDS signal through channel230 may act as a receive-clock and may be used for data capturing.

In one example, the delayed RDS signal may be communicated to data inputbuffer 480 through channel 486. The RDS may be communicated to thelatency error detection circuit 484 through channel 488. An errorresponse from circuit 484 may then be transmitted back to host CPU 108through interface connections 460, host internal bus interface 462, andresponse channel 476.

FIG. 5 shows a flow diagram outlining a method 500, according to anembodiment. For example, method 500 can detect an RDS signal andidentify valid, or delayed data read and transmission between peripheraldevice 104 and host device 102. It is to be appreciated that method 500may not occur in the order shown, nor include all operations shown.Merely for convenience, elements in FIGS. 1-4 will be used to performoperations shown in method 500.

In step 502, a read command and address is transmitted from a hostdevice interface to a peripheral device interface.

In step 504, once the peripheral device has obtained enough informationto identify the read command and begin access of the location, a counterin the host interface begins counting clock pulses generated from areference clock. In one example, a counter counts up from a zero value.It is to be appreciated by one skilled in the relevant art that othercounting schemes may be employed, such that the counter may be able totrack the latency values.

In step 506, a determination is made whether the RDS signal has beenreceived. Receiving the RDS signal refers to toggling of the signal fromone logic state to another. This may be from a high logic state to a lowlogic state, or vice-versa. The terms “arrival” and “reception” of theRDS signal may be interchangeably used herein to refer to toggling ofthe RDS signal from one logic state to another. If the RDS signal hasbeen received, data is reported from peripheral device 104 to hostdevice 102 (step 512). As such, the RDS signal may be used as a timereference to capture a read data at the host device interface 106. Oncea read data is reported to host device 102 (step 512), a determinationis made whether more data is expected (step 514). If more data isexpected, method 500 resets the count to zero and restarts at step 503,and if not, method 500 ends.

Returning to step 506, if the RDS signal is not received, method 500branches out to step 520, where the counter value is compared to apredetermined maximum latency. The predetermined maximum latency may beprogrammable and may be set by the software during an idle state of thesystem. There may be a plurality of predetermined latencies, for exampleone for the initial access time until the first set of data is sent backto host device 102 from the peripheral device 104, and a second latencyrelated to the delay in reading data at a boundary crossing between datapages in peripheral device 104.

If in step 522 the counter value is below the maximum predeterminedlatency, the method returns to step 504, i.e. the counter continues tocount until the RDS signal arrives. If the counter value is above themaximum predetermined latency before the RDS signal has been received,in step 524 the data is not sent to host device 102, and an error isreported in step 526, as the maximum waiting time for RDS signalreception has been exceeded. After one cycle has been completedaccording to method 500, the system may proceed to an idle state or asubsequent read operation (not shown in FIG. 5).

Method 500 may be used with a first predetermined maximum time ofreceipt and a second predetermined maximum time of receipt (not shown inFIG. 5). For example, method 500 may be used for receiving the RDSsignal before a first predetermined maximum time of receipt, therebycontrolling the latency from a read request to return of data for afirst data returned. Further, the RDS signal may be received at any timebefore a second predetermined maximum time of receipt. As such, method500 allow the controlling of the latency between data transfers toprovide flow control of a rate of transfers in a series of datatransfers. Further, method 500 allows receiving the RDS signal for eachdata element transfer of a plurality of data element transfers, when theread request is for the return of multiple read data elements.

The method of operation according to the embodiment described in FIG. 5indicates that the RDS signal 230 may serve an at least threefoldfunctionality. First, it may be used as a receive-data clock relayingtiming information and indicating when the data is valid on interfacebus 114, when the RDS signal in channel 230 is received. Second, it mayprovide variable latency information by delaying the first or subsequentdata transfers in a series of transfers. Third, it may indicate a readdata error and send an error response without data transmission fromperipheral device 104 to host device 102, when it is not received beforeexpiration of a time period corresponding to a predetermined maximumlatency time. It is to be appreciated by one skilled in the art thatadditional functionalities may be imparted to the RDS signal accordingto the various embodiments described herein.

According to one aspect of this disclosure, the read data error mayrefer to the initial access of a data page, or a page boundary crossingat a peripheral device, or any other operation that may require sometiming delay. The read operation may be any of single word read, burstread, where at least two words are read in sequence, or wrapped readwhere data read may begin for example in the middle of a page, continueuntil the end of an aligned block of the same word size, then return tothe beginning of the same word size block and continue to the pointwhere the data reading begun.

FIG. 6 shows a timing diagram 600 at an interface bus when there are noerrors in the data transmission, according to embodiments of thedisclosure. For example, data packets associated with a peripheraldevice that is a memory device are used. In this example there is apredetermined latency of five clock pulses. However, one skilled in thepertinent art may appreciate that it is not limited to this particulardevice or latency time and that similar timing diagrams may be producedfor other types of peripherals and plurality of first predeterminedlatency times, according to the example embodiment of this disclosure.

At time 602, a signal in chip select channel 220 and a RDS signal inchannel 230 toggle from a high logic state (“high”) to a low logic state(“low”) to indicate the onset of a read operation. At the same time 602,the read command and data address are sent from CPU 108, to peripheraldevice 104, through host interface 106 and interface bus 114. The datapackets transmitted from CPU 108 of host device 102 to peripheral device104 appear in data in/out channel 228 of the interface bus 114 duringtime period 604. For example, data packets “90”, “01”, “25”, “45”, “00”,“0E”, which are coded to indicate a read command and the addresslocation to peripheral device 104.

After time period 606, peripheral interface 110 has received adequateinformation to begin access of the memory. At this time, a counter (notshown) begins to count clock pulses as generated by the clock signal inchannel 222 and host interface 106 waits for the RDS signal in channel230. In this example, it is assumed that the initial value of thecounter has been set to zero, however, the implementation is not limitedto this counting scheme.

During time period 608, a five clock pulse latency occurs. RDS signal inchannel 230 toggles from low to high, indicating that it has beenreceived at host interface 106. At the same time, data in/out channel228 transmits data from peripheral device 104 back to host device 102,as indicated by the data packets “AB”, “CD”, “98”, “76”, which arevalidated by the rising and falling edges of the RDS signal in channel230.

In one implementation of this embodiment, the host interface 106 issuesa response through internal system bus 112 to CPU 108, corresponding tovalid transmission without error. This may be an “OKAY” response whenthe internal system bus is an AHB or AXI bus, but it is not limited tothis implementation.

FIG. 7 shows a timing diagram 700 at an interface bus when there is anerror after the initial access of a data page, according to embodimentsof the disclosure. In this example, there is a first predeterminedlatency of five clock pulses and the second predetermined latency isequal to the first predetermined latency. However, similar timingdiagrams can be produced for other predetermined latencies or for asecond predetermined latency greater than the first predeterminedlatency.

At time 702, a chip select signal in channel 220 and a RDS signal inchannel 230 toggle from high to low to indicate the onset of a readoperation. At the same time 702, the read command and data address aresent from CPU 108, to peripheral device 104, through host interface 106and interface bus 114. The data packets transmitted from CPU 108 of hostdevice 102 to peripheral device 104 appear in data in/out channel 228 ofinterface bus 114 during time period 704. For example, data packets“90”, “01”, “25”, “45”, “00”, “0E”, which are coded to indicate a readcommand and the address location to peripheral device 106.

After time period 706, peripheral interface 110 has received adequateinformation to begin access of the memory. At this time, a counterbegins to count clock pulses as generated by the clock 222 and hostinterface 106 waits for the RDS signal in channel 230. In this example,it is assumed that the initial value of the counter has been set tozero, however, the implementation is not limited to this countingscheme.

After time period 708 and five clock pulses, the RDS signal has nottoggled back to high, indicating an error in the data. The data is nottransmitted through the data in/out channel 228. In one implementationof this embodiment, host interface 106 issues an error response throughinternal system bus 112 to CPU 108, corresponding to error in the readdata. For example, the error message can be a “SLVERR” for an AXI or AHBinternal system bus, but it is not limited to this implementation.

FIG. 8 shows a timing diagram 800 at an interface bus when there is anerror at a page boundary crossing, according to embodiments of thedisclosure. In this example, there is a plurality of first predeterminedlatencies: one comprising five clock pulses and referring to the initialaccess latency, and one comprising three dock pukes and referring to alatency across a boundary crossing.

At time 802, the chip select signal in channel 220 and a RDS signal inchannel 230 toggle from high to low to indicate the onset of a readoperation. At the same time 802, the read command and data address aresent from CPU 108, to peripheral device 104, through host interface 106and interface bus 114. The data packets transmitted from CPU 108 of hostdevice 102 to peripheral device 104 appear in the data in/out channel228 of interface bus 114 during the time period 804. For example, datapackets “90”, “01”, “25”, “45”, “00”, “0E”, which are coded to indicatea read command and the address location to peripheral device 106.

After time period 806, the peripheral interface 110 has receivedadequate information to begin access of the memory. At this time, acounter begins to count clock pulses as generated by the clock inchannel 222 and host interface 106 waits for the RDS signal in channel230. In this example, it is assumed that the initial value of thecounter has been set to zero, however, the implementation is not limitedto this counting scheme.

During time period 808, a five clock pulse latency occurs. RDS signal inchannel 230 toggles from low to high, indicating that it has beenreceived at host interface 106. At the same time, data in/out channel228 transmits data from peripheral device 104 back to host device 102,as indicated by the data packets “AB”, “CD”, “98”, “76”, which arevalidated by the rising and falling edges of the RDS signal 230.

After the last data packet “76” has been transmitted across data in/outchannel 228, the RIDS signal in channel 230 has not toggled back to highbefore expiration of time period 810. Since the page boundary crossinglatency has been set to three clock pulses, this indicates a read dataerror across a page boundary. The data is not transmitted through datain/out channel 228, and an error response is sent to CPU 108.

It is to be appreciated that the Detailed Description section, and notthe Summary and Abstract sections (if any), is intended to be used tointerpret the claims. The Summary and Abstract sections (if any) may setforth one or more but not all exemplary embodiments of the invention ascontemplated by the inventor(s), and thus, are not intended to limit theinvention or the appended claims in any way.

While the invention has been described herein with reference toexemplary embodiments for exemplary fields and applications, it shouldbe understood that the invention is not limited thereto. Otherembodiments and modifications thereto are possible, and are within thescope and spirit of the invention. For example, and without limiting thegenerality of this paragraph, embodiments are not limited to the,hardware, methods and/or entities illustrated in the figures and/ordescribed herein. Further, embodiments (whether or not explicitly′described herein) have significant utility to fields and applicationsbeyond the examples described herein.

Embodiments have been described herein with the aid of functionalbuilding blocks illustrating the implementation of specified functionsand relationships thereof. The boundaries of these functional buildingblocks have been arbitrarily defined herein for the convenience of thedescription. Alternate boundaries can be defined as long as thespecified functions and relationships (or equivalents thereof) areappropriately performed. Also, alternative embodiments may performfunctional blocks, steps, operations, methods, etc. using orderingsdifferent than those described herein.

References herein to “one embodiment,” “an embodiment,” “an exampleembodiment,” or similar phrases, indicate that the embodiment describedmay include a particular feature, structure, or characteristic, butevery embodiment may not necessarily include the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it would be within the knowledge of persons skilled in therelevant art(s) to incorporate such feature, structure, orcharacteristic into other embodiments whether or not explicitlymentioned or described herein.

The breadth and scope of the invention should not be limited by any ofthe above-described exemplary embodiments, but should be defined only inaccordance with the following claims and their equivalents.

What is claimed is:
 1. A method comprising: transmitting addressinformation and a read request from a host interface to a peripheraldevice; counting clock pulses until a read data strobe signal isreceived from the peripheral device; using the read data strobe signalas a time reference; capturing data at the host interface using the timereference; in response to a number of the clock pulses being greaterthan a predetermined maximum latency: reporting an error to the hostinterface; and preventing capture of the data at the host interface. 2.The method of claim 1, further comprising: receiving the read datastrobe signal before a first predetermined maximum time of receipt; andcontrolling latency of the read request that initiates return of thedata from the peripheral device to the host interface.
 3. The method ofclaim 2, further comprising: receiving the read data strobe signalbefore a second predetermined maximum time of receipt; and controllinglatency between data transfers to provide control of a rate of transferin a series of data transfers from the peripheral device to the hostinterface.
 4. The method of claim 1, further comprising: when the readrequest is for a return of multiple data elements, receiving the readdata strobe signal for each data element transfer from the peripheraldevice to the host interface.
 5. The method of claim 1, wherein thepredetermined maximum latency comprises a number of pulses generated bya clock, the clock communicating from the host interface to theperipheral device.
 6. The method of claim 1, wherein the predeterminedmaximum latency is set by software in the host device at least beforeinitiating a data read operation.
 7. The method of claim 1, whereinreceiving data at the host interface when a number of the clock pulsesis less than or equal to the predetermined maximum latency furthercomprises receiving timing information at the host device that aids inthe capture of valid data.
 8. The method of claim 1, wherein preventingcapture of the read data at the host interface further comprisesreceiving, at the host device, data error information about a dataerror.
 9. The method of claim 5, wherein the data error occurs at one ofan initial data page access or a boundary crossing between data pages ofthe peripheral device.
 10. The method of claim 1, wherein receiving databefore an expected time of receipt or after a delay at the hostinterface comprises receiving variable timing information at the hostdevice.
 11. The method of claim 1, wherein a delay or a time periodbefore an expected time of receipt comprises the difference between thenumber of clock pulses until the read data strobe signal is received anda number of pulses comprising the predetermined maximum latency as setby the clock.
 12. The method of claim 3, wherein a read operationcomprises one of a single read, a continuous read, or a wrapped read.